Secure transactions using a point of sale device

ABSTRACT

Systems and methods are provided for secure transactions according to one or more embodiments. According to an embodiment, a method for providing secure transactions comprises initiating a transaction via a point of sale device having a one time password generator. The method also comprises generating at least one password by the point of sale device. The method further comprises associating the at least one password with account information. The method further comprises transmitting the password associated with the account information to a remote location. If the transmitted password matches predetermined associated information at the remote location, the method further comprises confirming the transaction.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of Ser. No. 12/571,290, filed Sep.30, 2009, which is incorporated herein by reference in its entirety.

BACKGROUND

1. Technical Field

Embodiments of the present disclosure generally relate to securetransactions, and more particularly, to methods and systems for securefinancial transactions using one or more point of sale devices andpasswords, PINs or passcodes for authentication.

2. Related Art

Financial transactions such as purchases made online or over theInternet are widely used and continue to grow in popularity. However,such financial transactions may introduce fraud and security concerns asa result of a seller not being able to physically identify a purchaserand verify that the purchaser is entitled to use a selected form ofpayment.

Financial transactions in general require some type of identityauthentication to verify that a purchaser is authorized to conduct sucha transaction. To address fraud and security concerns of financialtransactions, “two-factor authentication” systems have been introducedin connection with online and Internet purchases as well as forin-person purchases at a point of sale (POS) location. Two-factorauthentication systems require that a purchaser submit two unique formsof identification associated with the particular form of paymentselected by the purchaser. For example, a purchaser may be required topresent a primary account number (PAN) as well as a personalidentification number (PIN).

One effective second authentication factor may include the use of acard, for example, a credit card, that can display a “One-TimePIN/Password” or “OTP”. An OTP is similar to a traditional staticpassword in that it may be used along with a username or a PAN, however,an OTP is dynamically generated. At each session, a purchaser may usethe card displaying a unique multi-digit PIN or password. In subsequentsessions, yet another unique PIN or password is generated. These PINS orpasswords may be synchronized with a central server so that a purchaseris authenticated as an authorized purchaser.

An OTP may provide a higher level of security than a static password,PIN or other identifier. However, a need exists for improved methods andsystems for financial transactions with increased security features.

SUMMARY

As will be further described herein in relation to one or moreembodiments, methods and systems are provided for financial transactionsusing a point of sale device wherein security is enhanced while meetinga need for convenient, friendly and confidential payment exchangeswithin a trusted environment.

In accordance with an embodiment of the disclosure, a method forproviding secure transactions comprises initiating a transaction via apoint of sale device having a password generator. The method alsocomprises generating at least one password by the password generator ofthe point of sale device. The method also comprises associating the atleast one password with account information. The method furthercomprises transmitting the at least one password associated with theaccount information to a remote location. If the transmitted passwordmatches predetermined associated information maintained at the remotelocation, the method also comprises confirming the transaction.

In accordance with another embodiment of the disclosure, a point of saledevice comprises: one or more processors; and one or more memoriesadapted to store a plurality of machine-readable instructions which whenexecuted by the one or more processors are adapted to cause the point ofsale device to: read information related to a user's selected form ofpayment, generate at least one password associated with the readinformation, and transmit the at least one password to a remotelocation.

In accordance with another embodiment of the disclosure, a securetransaction system comprises a point of sale device in communicationwith a remote location via a network. The system also comprises one ormore processors and one or more memories adapted to store a plurality ofmachine-readable instructions. When executed by the one or moreprocessors, the machine-readable instructions are adapted to cause thesecure transaction system to facilitate a transaction initiated via thepoint of sale device having a password generator; receive at least onepassword generated by the point of sale device; associate the at leastone password generated by the point of sale device with accountinformation; if the transmitted password matches predeterminedassociated information, authorizing the financial transaction.

In accordance with another embodiment of the disclosure a method forproviding secure transactions comprises initiating a transaction via apoint of sale (POS) device using a user-selected form of payment. Themethod also comprises reading information from the user-selected form ofpayment, wherein the read information comprises at least a password,account information and a digital signature of the user-selected form ofpayment. The method also comprises generating at least one POS passwordassociated with the information read from the user-selected form ofpayment. The method further comprises transmitting information to aremote location wherein the transmitted information comprises at leastthe information read from the user-selected form of payment, the atleast one POS password and a POS digital signature; and confirming thetransaction if the transmitted information matches predeterminedassociated information maintained at the remote location.

These and other features and advantages of the embodiments of thepresent disclosure will be more readily apparent from the detaileddescription of the embodiments set forth below taken in conjunction withthe accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a block diagram illustrating a system for processing financialtransactions according to an embodiment of the present disclosure.

FIG. 2 is a block diagram illustrating components inside a terminal orpoint of sale (POS) device according to an embodiment of the presentdisclosure.

FIG. 3 is a flowchart for a secure financial transaction according to anembodiment of the present disclosure.

FIG. 4 is a flowchart for a secure financial transaction according toanother embodiment of the present disclosure.

Like element numbers in different figures represent the same or similarelements.

DETAILED DESCRIPTION

In accordance with one or more embodiments described herein, methods andsystems are provided for secure transactions such as financialtransactions at a point of sale (POS) location using passwords, PINs orpasscodes. In financial transactions where a purchaser desires to payfor goods and/or services, a terminal or point of sale (POS) device maybe used by a merchant or service provider to process the payment. Theterminal or POS device is able to generate a password, PIN or passcodesuch as a one time password (OTP) based on, for example, a user'saccount information and/or the particular merchant's terminalinformation. The password, PIN or passcode may then be sent for paymentverification from the terminal or POS device to a remote location, forexample, a payment service provider, and may be matched withpredetermined information maintained at the remote location. If there isa match, then the financial transaction is confirmed. If there is nomatch, then the financial transaction is rejected.

In addition, the terminal or POS device may read a password, PIN orpasscode such as an OTP from a user's transaction card (e.g., a creditcard) having the OTP as well as account information such as a primaryaccount number (PAN) along with a digital signature of the transactioncard. The terminal or POS device may also generate a POS password, PINor passcode such as an OTP and a POS digital signature. The terminal orPOS device may then send the transaction card's account information, thecard's OTP and the card's digital signature as well as the POS's OTP anddigital signature to a remote location, for example, to a paymentservice provider, for verification or confirmation over an Omnibus orover a network. The OTP and digital signature combination informationprovides added security against potential fraudulent use. In one or moreembodiments described herein, transactions at a terminal or POS deviceusing passwords, PINs or passcodes may be performed in a secure mannerwhile avoiding potential payment disputes.

Referring now to the drawings wherein the showings are for purposes ofillustrating embodiments of the present disclosure only, and not forpurposes of limiting the same, FIG. 1 is a block diagram illustrating asystem for processing financial transactions according to an embodimentof the present disclosure.

In system 100, a user desiring to purchase goods and/or services mayselect to pay for such goods and/or services with a transaction card102. Transaction card 102 may be, for example, a smart card, or atraditional credit card or debit card issued by a financial institution.Transaction card 102 may include account information that may be printedon a front portion of the transaction card 102. Account information mayinclude, for example, a personal account number (PAN), an expirationdate, a security code and/or the name of an authorized user. Thisaccount information may also be stored on a magnetic stripe 103 that maybe located on a back portion of the transaction card 102. When the userpresents transaction card 102 to a salesperson at a merchant's locationto pay for goods and/or services, the salesperson may swipe transactioncard 120 on a magnetic stripe card reader included in a merchant'sterminal or point of sale device (POS) 104. In other embodiments,magnetic stripe 103 of transaction card 102 may be replaced by, or beprovided in addition to, a near field communications (NFC) transponderincluding, for example, an RFID chip, a contactless smart card, etc. Inthis case, POS 104 may read the transaction card's information via useof the NFC transponder. Transaction card 102 may also include a displaycapable of displaying alphanumeric characters, graphics, etc. Suchdisplay may be an electro-optic display such as a flexible LCD screen, alight emitting polymer display, etc. as generally known in the art.

In one or more embodiments, transaction card 102 may generate a passwordsuch as a one time password (OTP) as well as a digital signature oftransaction card 102. Transaction card 102 may include a processorconfigured to provide OTPs to magnetic stripe 103, to the card's NFCtransponder and/or to the display of transaction card 102.

Alternatively, a user desiring to purchase goods and/or services mayselect to pay for such goods and/or services using a client device 110at POS 104. Client device 110 may be implemented using any appropriatecombination of hardware and/or software configured for wired and/orwireless communication over a network. For example, client device 110may be implemented as a wireless telephone, a personal digital assistant(PDA), a key fob, a smart card, a notebook computer and/or other typesof computing devices. In one embodiment, client device 110 may beimplemented as a personal computer of a user in communication with theInternet or another network.

Client device 110 may include an Application component or block(Application block) where applications may be loaded. One applicationthat may be loaded in the Application block is a mobile paymentapplication wherein client device 110 is adapted to be used as a mobilewallet. Client device 110 may also include an RFID device, Bluetooth, anear field communication (NFC) transponder or an infrared communicationdevice to communicate account information to POS 104 that may be storedin the mobile wallet of client device 110 upon initiation of atransaction. Account information may include a PAN, expiration date anda password or personal identifier such as a personal identificationnumber (PIN). In one or more embodiments, client device 110 may generatepasswords such as OTPs and have a digital signature particular to clientdevice 110.

It should be appreciated that components of client device 110 includingthe Application block may also include a Secure Element (SE), aUniversal Integrated Circuit Card (UICC) with a Subscriber IdentityModule (SIM) application, smart cards or other suitable devices.

The Application block may also include other pre-loaded applications,for example, a payment service provider application to facilitatefinancial transactions. In addition, client device 110 may includevarious applications as may be desired in particular embodiments toprovide desired features to client device 110.

Client device 110 may further include identification information suchas, for example, a Secure Element number or identification (ID), theclient device's unique identifier number such as an International MobileEquipment Identity (IMEI) number, or a unique number associated with auser of a client device such as an International Mobile SubscriberIdentity (IMSI) number, which may be stored inside the client device,for example, in a component such as an SE, a UICC/SIM card, a smart cardor any other suitable card of the client device. One or more useridentifiers may be implemented, for example, as operating systemregistry entries, cookies associated with a browser application,identifiers associated with hardware of client device 110, or otherappropriate identifiers.

Upon a user's selection of a form of payment, for example, by atransaction card 102 or a client device 110, POS 104 may initiate aconnection to a remote location 108, which may include for example apayment service provider, via a network 106. POS 104 is adapted togenerate at least one password, PIN or passcode such as a one timepassword (OTP) upon initiation of a transaction as will be described inmore detail below according to one or more embodiments. The password,PIN or passcode generated by POS 104 may be associated with informationread by POS 104 such as account information from, for example, magneticstripe 103 of transaction card 102, or received by POS 104 from clientdevice 110. POS 104 may then transmit the generated password andassociated account information via network 106 to remote location 108.

Furthermore, in one or more embodiments, transaction card 102 or clientdevice 110 may be configured to generate a password such as a one timepassword (OTP) as well as a digital signature. As is known in the art,digital signatures are provided to authenticate the sender ofinformation, for example, in this case, the transaction card or theclient device. The importance of high confidence in sender authenticityis especially obvious in a financial context. POS 104 may be adapted toread such OTPs and digital signatures along with other accountinformation from the form of payment selected by the user. POS 104 mayalso transmit the digital signature and OTPs generated by transactioncard 104 or client device 110 to remote location 108.

In addition, transaction information including a merchant identifier, aterminal identifier, a date, a time, a payment amount, etc. may betransmitted to remote location 108 by POS 104. Remote location 108 maystore some of the received account and/or transaction information andauthenticate the password generated and received from POS 104 accordingto the account/transaction information. The transaction may be confirmedor rejected depending on whether the received information, for example,a one time password, matches pre-determined information maintained atremote location 108. In one embodiment, a user identifier may be used byremote location 108 to associate transaction card 102 or client device110 (or correspondingly the user) with a particular account maintainedby remote location 108. Once confirmed, remote location 108 may send aconfirmation message to POS 104 indicating that the transaction has beenauthenticated. Conversely, if the transaction is rejected, remotelocation 108 may reply that the transaction was denied.

Remote location 108 may include a payment service provider such asPayPal, Inc. of San Jose, Calif., or one or more financial institutions,or a respective intermediary that may provide multiple POS devices atvarious locations to facilitate transaction routings between merchantsand, for example, financial institutions. Remote location 108 maymaintain data or information related to, for example, accountinformation, passwords, PINs, passcodes, merchant or terminalidentifiers, and/or client device information such as client deviceidentifiers. For example, an OTP generated by POS 104 may be associatedwith an account number or a name or a client device identifier as wellas with a merchant or terminal identifier. An OTP may also be associatedwith a unique account or with a unique client device (having multipleaccounts). Data or information may be stored according to variousschemes for coordinating accounts, passwords, PINs or passcodes, clientdevices and merchant information.

POS 104, transaction card 102, client device 110 and remote location108, for example, a payment service provider, may each include one ormore processors, memories, and other appropriate components forexecuting instructions such as program code and/or data stored on one ormore computer readable mediums to implement the various applications,data, and methods described herein. For example, such instructions maybe stored in one or more computer readable mediums such as memories ordata storage devices internal and/or external to various components ofthe system, and/or accessible over network 106, which may be implementedas a single network or a combination of multiple networks. For example,in various embodiments, a network may include the Internet or one ormore intranets, landline networks, wireless networks, and/or otherappropriate types of networks.

Referring now to FIG. 2, a block diagram illustrating components insidea terminal or point of sale (POS) device is provided according to anembodiment of the present disclosure.

Point of sale device (POS) 104 may include various components, forexample, at least an input 206, a port 208, a password generator 210, aprocessor 212 and a memory 214. Processor 212 may be communicativelyconnected and adapted to control the components of POS 104 according to,for example, software commands stored in memory 214.

Input 206 of POS 104 is adapted to receive data such as accountinformation necessary to support a transaction. For example, input 206may include a keypad or a keyboard for manually entering transactioninformation such as a PAN, a money amount, a password, etc. Input 206may also include a magnetic stripe reader, an RFID chip, Bluetooth, anNFC transponder, an IR communications reader, etc. in order to receivedata from a transaction card 104, a client device 110, or the like. Inaddition, input 206 is adapted to read a password, PIN or passcode suchas an OTP generated by the form of payment selected by the user, forexample, transaction card 102 or client device 110. Furthermore, input206 of POS 104 may be adapted to read a digital signature of theselected form of payment, which may enhance the security of atransaction.

Port 208 may be adapted to facilitate communications for POS 104, forexample, wired or wireless communications, communications via antennas,Internet, or other network communications.

According to one or more embodiments, password generator 210 of POS 104is adapted to generate passwords, PINs or passcodes, including one-timepasswords, PINs or passcodes (OTPs). Upon an initiation of a transactionat POS 104, POS 104 interacts with the form of payment selected by theuser, for example, by swiping a transaction card or by a Near FieldCommunications (NFC) transponder for a client device. Processor 212 ofPOS 104 causes password generator 210 to generate a password, PIN orpasscode such as an OTP associated with account information read fromthe form of payment selected by the user, for example, a transactioncard or a client device, as well as with transaction informationincluding, for example, merchant or terminal identifier information. Theassociated password, PIN or passcode may then be transmitted to a remotelocation 108 via a network. Passwords, PINs or passcodes such as OTPsmay be automatically generated in a random manner, by an algorithm usingone or more unique features related to a device, or they may also begenerated based on pre-determined information. OTPs may be updatedregularly based on, for example, time with an expiration or a timestamp. POS 104 may generate passwords, PINs or passcodes for differentaccounts, users or client devices.

POS 104 may be any physical device at any location where a user may makea payment for purchased goods and/or services. POS 104 may generally belocated at a merchant's establishment where a salesperson operates POS104. Alternatively, the user may self operate the POS 104, for example,at vending machines, ATMs, ticket dispensers, etc. In one example, POS104 may be implemented as a phone-based POS wherein a merchant may use awireless telephone to receive payment. Other examples of POS 104 includevirtual terminals, personal computers, notebook computers, cashregisters or any other devices that are adapted to read a magneticstripe, an RFID chip, Bluetooth, NFC, IR communications, etc. from atransaction card 104, a client device 110, or the like.

Referring now to FIG. 3, a flowchart for a secure financial transactionis illustrated according to an embodiment of the present disclosure.FIG. 3 may be implemented by the system of FIG. 1 and the POS device ofFIG. 2 according to one or more embodiments.

In block 302, a secure transaction such as a financial transaction maybe initiated upon a user selecting and using a form of payment such as atransaction card or a client device via a POS device. In an example, theuser may approach a salesperson at a merchant's location to pay forcertain goods and/or services using, for example, a transaction cardsuch as a credit card or a client device such as a mobile telephone. Thesalesperson would generally use a POS device to process the payment, forexample, by swiping a credit card through a magnetic stripe reader ofthe POS, or by using an NFC reader of the POS to read payment andaccount information from the mobile telephone.

In block 304, a password, PIN or passcode such as a one time password,PIN or passcode (OTP) is generated by a password generator of the POSdevice. For example, one time passwords may be generated atpredetermined time intervals. Passwords, PINs or passcodes may beautomatically generated for a specific account or for a specific form ofpayment selected by the user using random numbers or other appropriateidentification tokens, or using the OATH open standard as is known inthe art.

In block 306, the generated password, PIN or passcode is associated withaccount or transaction information including for example, a primaryaccount number (PAN), a name, a phone number, an email address, a clientdevice identifier, a POS identifier, a merchant identifier, etc.

In block 308, the associated password, PIN or passcode is transmitted toa remote location via a network.

In block 310, the transmitted associated password is compared withpredetermined information at the remote location. The remote location isadapted to identify a particular account, user, client device, merchantidentifier, terminal or POS associated with the received password basedon pre-determined or pre-registered information maintained therein. Forinstance, the remote location may maintain a database associating, atleast, financial accounts, passwords and specific devices. In anexample, an account number may be associated with a password and a formof payment selected by the user including a client device identifier, amobile telephone number, or the like.

In block 312, if the transmitted associated password does not match thepredetermined associated information at the remote location, thefinancial transaction is rejected. For instance, if the transmittedassociated password does not match, for example, an account number, atelephone number, a money amount limit, etc., as maintained in adatabase at the remote location, the remote location may send a messageto the POS so that the transaction is rejected.

In block 314, if the transmitted associated password matchespredetermined associated information at the remote location, thefinancial transaction is confirmed. For instance, if the transmittedassociated password matches, for example, an account number, a telephonenumber, a money amount limit, etc., as maintained in a database at theremote location, the remote location may send a message to the POS sothat the transaction is confirmed.

According to one or more embodiments of the present disclosure, a strongsecond factor authentication may be provided to verify the authenticityof a transaction card, a client device, a user, a merchant, etc. Forexample, a payment service provider may compare a one time passwordgenerated by a POS with pre-registered identification information for aparticular user, a particular client device or a particular merchant(also referred to as an identifier).

Identification information for a particular user, client device ormerchant may be set during pre-registration with the remote location.According to one or more embodiments, it is assumed that a user or amerchant has previously registered with the remote location, forexample, to open an account. In this regard, it will be appreciated thatthe user or merchant may have previously provided account information tothe remote location, for example, over network 106 through, for example,a secure connection between client device 110 or POS 104 and remotelocation 108. Alternatively, client device 110 or POS 104 may bepersonalized during customization by operators, customizers and/ordevice manufacturers.

As a result of such previous registration, client device 110 or POS 104stores a specific user or merchant identifier, respectively, that may beused to identify the particular user or merchant as having an accountmaintained by remote location 108. The user or merchant identifier maybe implemented, for example, as one or more cookies, operating systemregistry entries, hardware identifiers, or other types of identifiers.

When a transaction, for instance a financial transaction using a paymentservice provider such as PayPal, Inc. with client device 110 ortransaction card 102, the payment service provider gets signatureinformation of, for example, a X509 certificate. This X509 signatureinformation is typically maintained for each user. The signatureinformation may be a digital signature and may include a time stamp,dollar amount, transaction type, item, and location, which may bedetermined from a GPS enabled client device 110. Signature informationmay also be preloaded in client device 110 as EMV (Europay, MasterCard,Visa), or ECC, in addition to X509.

Referring now to FIG. 4, a flowchart for a secure financial transactionaccording to another embodiment of the present disclosure is provided.FIG. 4 may be implemented by the system of FIG. 1 and the POS device ofFIG. 2 according to one or more embodiments.

In block 402, as described above according to one or more embodiments, asecure transaction such as a financial transaction may be initiated upona user selecting and using a form of payment such as a transaction cardor a client device via a POS device.

In block 404, the POS device is adapted to receive or read informationfrom a form of payment selected by a user such as a transaction card, aclient device, etc. The information read from the form of paymentselected by the user may include, at least, account information and apassword, PIN or passcode such as an OTP associated with or generated bythe form of payment selected by the user. The POS device is also adaptedto receive or read a digital signature corresponding to the form ofpayment selected by the user.

In block 406, as described above according to one or more embodiments, apassword, PIN or passcode such as a one time password, PIN or passcode(OTP) is generated by a password generator of the POS device. This POSpassword, PIN or passcode may be generated based on particularinformation including information received or read from the form ofpayment selected by the user as well as unique information related tothe merchant or the POS device itself. It should be noted that the POSdevice may also have a POS digital signature associated therewith.

In block 408, the POS device is adapted to transmit informationincluding the POS generated password, PIN or passcode and the POSdigital signature to a remote location, for example, a payment serviceprovider. In addition, the POS device is adapted to transmit thepassword, PIN, or passcode, account information and digital signaturereceived or read from the form of payment selected by the user to theremote location.

In block 410, the transmitted information is compared with predeterminedinformation at the remote location. As described above according to oneor more embodiments, the remote location is adapted to authenticate aparticular digital signature, account, user, client device, merchantidentifier, terminal, POS device identifier, or the like, associatedwith the transmitted information based on pre-determined orpre-registered information maintained therein.

In block 412, if the transmitted information does not match thepredetermined associated information at the remote location, thefinancial transaction is rejected.

In block 414, if the transmitted combination information matchespredetermined associated information at the remote location, thefinancial transaction is confirmed.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the spirit of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components, andvice-versa.

Software in accordance with the present disclosure, such as program codeand/or data, may be stored on one or more computer readable mediums. Itis also contemplated that software identified herein may be implementedusing one or more general purpose or specific purpose computers and/orcomputer systems, networked and/or otherwise. Where applicable, theordering of various steps described herein may be changed, combined intocomposite steps, and/or separated into sub-steps to provide featuresdescribed herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. It iscontemplated that various alternate embodiments and/or modifications tothe present disclosure, whether explicitly described or implied herein,are possible in light of the disclosure. For example, although financialtransactions have been described according to one or more embodiments,it should be understood that the present disclosure may also apply totransactions where requests for information, requests for access, orrequests to perform certain other transactions may be involved.

Having thus described embodiments of the disclosure, persons of ordinaryskill in the art will recognize that changes may be made in form anddetail without departing from the scope of the disclosure. Thus thedisclosure is limited only by the claims.

What is claimed is:
 1. A system comprising: one or more processors; and one or more memories adapted to store a plurality of machine-readable instructions which when executed by the one or more processors are adapted to cause the system to: receive information comprising at least one One-Time Password (OTP) generated by a point of sale (POS) device having an OTP generator in connection with a transaction conducted via the POS, wherein the OTP is associated with account information and one or more unique identifiers; and confirm the transaction if the received information matches predetermined information including one or more pre-registered unique identifiers.
 2. The system of claim 1, wherein the plurality of machine-readable instructions are further adapted to cause the system to: receive the information comprising the OTP generated by the POS device, wherein the OTP is associated with at least one of user's account information and a merchant's account information.
 3. The system of claim 1, wherein the plurality of machine-readable instructions are further adapted to cause the system to: receive the information comprising the OTP generated by the POS device, wherein the OTP is generated by the password generator of the POS device itself based on information read from a form of payment selected by a user that includes a password associated with or generated by the form of payment selected by the user as well as unique information comprising one or more unique identifiers related to the merchant or the POS device itself.
 4. The system of claim 1, wherein the plurality of machine-readable instructions are further adapted to cause the system to: receive the information, wherein the received information further comprises a password read by the POS, wherein the password is generated by a form of payment selected by a user to pay for goods and/or services, and a digital signature of the form of payment along with the at least one OTP generated by the POS password generator of the POS device and a digital signature of the POS device.
 5. The system of claim 1, wherein the plurality of machine-readable instructions are further adapted to cause the system to: confirm the transaction if the received information matches the one or more pre-registered unique identifiers including at least one of a primary account number (PAN), an address, a location, a time, a Secure Element number or identification (ID), an International Mobile Equipment Identity (IMEI) number of a client device, and a user-associated International Mobile Subscriber Identity (IMSI) unique number stored in a component inside the client device.
 6. The system of claim 1, wherein the plurality of machine-readable instructions are further adapted to cause the system to: receive the information comprising the OTP(s) wherein the OTP(s) is associated with account information that is read at least in part from a user-selected form of payment.
 7. The system of claim 6, wherein the plurality of machine-readable instructions are further adapted to cause the system to: receive the information comprising the OTP(s) wherein the OTP(s) is associated with account information that is read at least in part from the user-selected form of payment, wherein the user-selected form of payment further comprises a transaction card or a client device to pay for goods and/or services.
 8. The system of claim 1, wherein the plurality of machine-readable instructions are further adapted to cause the system to: receive the information comprising the OTP)(s) wherein the OTP(s) is associated with account information, wherein the account information further comprises at least one of a primary account number (PAN), a name, a phone number, an email address, a client device identifier, a POS identifier, and a merchant identifier.
 9. The system of claim 1, wherein the POS device is provided by a merchant or a service provider.
 10. A method comprising: receiving, electronically by a processor, information comprising at least one One-Time Password (OTP) generated by a point of sale (POS) device having an OTP generator in connection with a transaction conducted via the POS, wherein the OTP is associated with account information and one or more unique identifiers; and confirming, electronically by the processor, the transaction if the received information matches predetermined information including one or more pre-registered unique identifiers.
 11. The method of claim 10, further comprising: receiving, electronically by the processor, the information comprising the OTP generated by the POS device, wherein the OTP is associated with at least one of user's account information and a merchant's account information.
 12. The method of claim 10, further comprising: receiving, electronically by the processor, the information comprising the OTP generated by the POS device, wherein the OTP is generated by the password generator of the POS itself based on information read from a form of payment selected by a user that includes a password associated with or generated by the form of payment selected by the user as well as unique information comprising one or more unique identifiers related to the merchant or the POS device itself.
 13. The method of claim 10, further comprising: receiving, electronically by the processor, the information, which further comprises a password read by the POS, wherein the password is generated by a form of payment selected by a user to pay for goods and/or services, and a digital signature of the form of payment along with the at least one OTP generated by the POS password generator of the POS device and a digital signature of the POS device.
 14. The method of claim 10, further comprising: confirming, electronically by the processor, the transaction if the received information matches the one or more pre-registered unique identifiers including at least one of a primary account number (PAN), an address, a location, a time, a Secure Element number or identification (ID), an International Mobile Equipment Identity (IMEI) number of a client device, and a user-associated International Mobile Subscriber Identity (IMSI) unique number stored in a component inside the client device.
 15. The method of claim 10, further comprising: receiving, electronically by the processor, the information comprising the OTP(s) wherein the OTP(s) is associated with account information that is read at least in part from a user-selected form of payment.
 16. The method of claim 15, further comprising: receiving, electronically by the processor, the information comprising the OTP)(s) wherein the OTP(s) is associated with account information that is read at least in part from the user-selected form of payment, wherein the user-selected form of payment further comprises a transaction card or a client device to pay for goods and/or services.
 17. The method of claim 10, further comprising: receiving, electronically by the processor, the information comprising the OTP(s) wherein the OTP(s) is associated with account information, wherein the account information further comprises at least one of a primary account number (PAN), a name, a phone number, an email address, a client device identifier, a POS identifier, and a merchant identifier.
 18. The method of claim 10, wherein the POS device is provided by a merchant or a service provider.
 19. A non-transitory computer readable medium on which are stored computer readable instructions and, when executed by a processor, cause the processor to: receive information comprising at least one One-Time Password (OTP) generated by a point of sale (POS) device having an OTP generator in connection with a transaction conducted via the POS, wherein the OTP is associated with account information and one or more unique identifiers; and confirm the transaction if the received information matches predetermined information including one or more pre-registered unique identifiers.
 20. The non-transitory computer readable medium of claim 19, wherein the readable instructions, when executed by the processor, further cause the processor to: confirm the transaction if the received information matches the one or more pre-registered unique identifiers including at least one of a primary account number (PAN), an address, a location, a time, a Secure Element number or identification (ID), an International Mobile Equipment Identity (IMEI) number of a client device, and a user-associated International Mobile Subscriber Identity (IMSI) unique number stored in a component inside the client device. 